You can upgrade XCO in a multi-node, high-availability deployment.
		About this task
Follow this procedure to upgrade XCO in a
			multi-node deployment using interactive mode.The upgrade process takes approximately 10
				to 15 minutes to complete. During the upgrade process, XCO services are down but
				users or automated systems can continue to make calls into XCO. 
The upgrade process
				automatically backs up the XCO database to recover data if the
				upgrade fails. You can apply this procedure on either of the nodes.
		Procedure
- 
				Download the image (*.tar.gz) to
					a new sub-folder.
			
- 
				Verify the PGP signature as
					described in article 48172 on the Extreme Portal.
			
- 
				Untar the image.
				
					device# tar -xvzf efa-v3.x.x.tar.gz 
 
- 
				Change to the XCO directory.
				
			
- 
				Run the deployment script.
				
					device# source deployment.sh 
 
					The XCO Installer begins in a series of dialogs. 
 
- 
				When prompted, select Upgrade or Redeploy.
			
- 
				When prompted, enter the virtual
					IPv6 address for the cluster.
				
					
						- Select Yes and then provide the virtual IPv6
							addresses.
- Select No to ignore this optional step.
 
 
- 
				When prompted to configure
					additional IP addresses for a health check, take one of the following
					steps.
				
					
						- Select Yes and
							then provide the IP addresses.
- Select No to
							ignore this optional step.
 
 
- 
				When prompted to configure additional management IP networks, take one of the
					following steps.
				
					 Note    XCO management Interface must have both IPv4 and IPv6 address configured.
							Adding IPv6 address is optional while IPv4 is mandatory during sub
							interface creation. You can add only one management IP networks during
							upgrade. After the upgrade, you can add more than one management IP
							networks. 
						- Select Yes and
							then provide the following information when prompted. Repeat as often as
								necessary.
								- Sub-interface
									name, which is a unique name that contains no more than 11
									characters, no white space, and no % or /
									characters.
- ID of the VLAN
									that the management network uses to tag traffic. Valid values
									range from 2 through 4090.
- IP subnet address
									in CIDR format. The subnet must not overlap with any IP subnet
									that you have already provided.
  Note    An IPv6 address is optional, but an IPv4 address is
								mandatory. 
- Select No to ignore this optional step or when
							you have finished entering network information.
 
 
- 
				When prompted to configure
					additional management IP network routes, take one of the following steps.
				
					An IPv6 address is optional, but an IPv4 address is mandatory. 
						- Select Yes and
							then provide the following information when prompted. Repeat as often as
								necessary.
								- Target network IP
									address in CIDR format 
- Source IP address
									for outbound traffic
- Next-hop or
									gateway IP address through which access to the destination
									network is provided
 
- Select No to
							ignore this optional step or when you have finished entering route
							information.
 
 As the installation proceeds,
					messages display showing the installation progress. 
- 
				Verify the upgrade.
				
					- 
						From the XCO command line, run the sudo efactl
								status command to see the status of nodes, pods, and
							services. 
					
- 
						From the XCO command line, run
							the efa
								status command to ensure that all nodes are up.